You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For FileTree I have found it necessary to put in validation checks that the method protocol for class extensions matches the package name .... human beings will be editing the files by hand and they will be cutting and pasting, so these kind of detail errors will happen ... the consequence of not validating is that the package structure will be immediately corrupted once the incorrect protocol names are loaded into the system ... same thing should probably go for regular classes where the method protocol needs to NOT be a package name ...
Class categories are the same ... the category of the class has to match the name of the package ...
The text was updated successfully, but these errors were encountered:
For FileTree I have found it necessary to put in validation checks that the method protocol for class extensions matches the package name .... human beings will be editing the files by hand and they will be cutting and pasting, so these kind of detail errors will happen ... the consequence of not validating is that the package structure will be immediately corrupted once the incorrect protocol names are loaded into the system ... same thing should probably go for regular classes where the method protocol needs to NOT be a package name ...
Class categories are the same ... the category of the class has to match the name of the package ...
The text was updated successfully, but these errors were encountered: