Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

category property for class and package membership can become out of sync #136

Closed
dalehenrich opened this issue Jan 31, 2015 · 1 comment

Comments

@dalehenrich
Copy link
Owner

While doing a merge for a "renamed" package, I made the mistake of moving a class properties file (with the category set to the old package name) into the new package and when filetree creates the class in the other category, the class is effectively moved to a different package ... since the category pretty much needs to stay in sync with the package, I think an error should be thrown if a class is loaded whose category is not consistent with the package that the class resides within ...

@dalehenrich
Copy link
Owner Author

extension method categories also need to conform...

dalehenrich added a commit that referenced this issue Jan 31, 2015
…hod category are not consistent with the package name
dalehenrich added a commit that referenced this issue Jan 31, 2015
dalehenrich added a commit that referenced this issue Jan 31, 2015
dalehenrich added a commit that referenced this issue Jan 31, 2015
fix for Issue #136
Conflicts:

	repository/MonticelloFileTree-Core.package/MCFileTreeStCypressReader.class/instance/addClassDefinitionFrom.comment..st
	repository/MonticelloFileTree-Core.package/MCFileTreeStCypressReader.class/instance/addExtensionClassAndMethodDefinitionsFromEntry..st
	repository/MonticelloFileTree-Core.package/MCFileTreeStCypressReader.class/instance/addMethodDefinitionsForClass.methodProperties.in..st
dalehenrich added a commit that referenced this issue Jan 31, 2015
dalehenrich added a commit that referenced this issue Jan 31, 2015
dalehenrich added a commit that referenced this issue Jan 31, 2015
…sable validation due to GsDevKit/gsDevKitHome#53

Conflicts:

	repository/MonticelloFileTree-Tests.package/MCFileTreeIssue136Test.class/instance/expectedFailures.st
	repository/MonticelloFileTree-Tests.package/MCFileTreeIssue136Test.class/instance/tearDown.st
dalehenrich added a commit that referenced this issue Feb 1, 2015
…#136

Conflicts:
	repository/MonticelloFileTree-Tests.package/MCFileTreeIssue136Test.class/instance/expectedFailures.st
	repository/MonticelloFileTree-Tests.package/MCFileTreeIssue136Test.class/instance/tearDownPackagesList.st

Conflicts:

	repository/MonticelloFileTree-Tests.package/MCFileTreeIssue97Test.class/instance/testLoad.st
dalehenrich added a commit that referenced this issue Feb 1, 2015
Conflicts:
	repository/MonticelloFileTree-Tests.package/MCFileTreeIssue136Test.class/instance/testClassError.st
	repository/MonticelloFileTree-Tests.package/MCFileTreeIssue136Test.class/instance/testExtensionMethodError.st
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant