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

Fix Issue #350: Add test case for verifying the IfcMaterialLayerSet name (LayerSetName) in material test cases #351

Open
wants to merge 3 commits into
base: development
Choose a base branch
from

Conversation

giuseppeverduciALMA
Copy link
Contributor

@giuseppeverduciALMA giuseppeverduciALMA commented Sep 27, 2024

This pull request addresses the missing test case for verifying the name (LayerSetName) of the IfcMaterialLayerSet element in the material test cases (Issue #350).

Changes:

  • updated the script.md file to include the new test case
  • included the generated ids file
  • added a sample IFC file that includes an IfcMaterialLayerSet with a defined value for the LayerSetName attribute
  • updated the .gitignore file to prevent compiled files from being inadvertently added to the repository

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @giuseppeverduciALMA,

Aren't these match expression a bit too broad? I'm concerned the will end up excluding useful files

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right to point that out; I see how the match expressions in the .gitignore could potentially be too broad. The intent was to exclude only generated and compiled files specific to the build process, especially those in the SchemaProject and build directories, which are recreated with each compilation and don't exist in the source repository.

For example, with a modification like this:

build/bin
build/obj
SchemaProject/bin
SchemaProject/obj

we would exclude only the files resulting from the compilation while still allowing the commit of the SchemaProject/Ids.cs file, which is autogenerated (would it be helpful to keep this file?).

How could we further refine these expressions to minimize any risk of excluding useful files?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we already have similar matches in the current gitignore, I wonder if you need a local "git clean -xdf" and see if you still have undesired artifacts after compilation.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've removed the two entries from the .gitignore after running the clean command. Thanks for the guidance!

Copy link
Contributor

@CBenghi CBenghi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Content is ok, I'm unsure about the changes to the .gitignore file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants