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

revC1: Added BOM management keys to the schematic. #129

Merged
merged 1 commit into from Apr 16, 2019
Merged

Conversation

esden
Copy link
Member

@esden esden commented Apr 16, 2019

This is needed for 1BitSquared production management.

@whitequark
Copy link
Member

Does it have to be "Key" specifically? It's a bit weird to have 1BitSquared-specific fields that aren't actually related to 1BitSquared just from their name.

@esden
Copy link
Member Author

esden commented Apr 16, 2019

It is just how I call them all across my own designs, and is in the KiCad field template all across my machines. To be fair you could use these keys to manage bom's across more than one project too. If you want I can rename it to some other field name. The keys are pretty self explanatory and could be used by others too. It is not like some super cryptic hash or anything. :D

@whitequark
Copy link
Member

I think it's best if you rename them. The reason is that while the keys may be used by others (maybe), you're the one who modifies them, since if someone else does that it no longer works with your system.

This is needed for 1BitSquared production management.
@esden
Copy link
Member Author

esden commented Apr 16, 2019

Fair enough. I renamed the "Key" to "1b2-bom-key".

@whitequark whitequark merged commit e601fab into master Apr 16, 2019
@whitequark whitequark deleted the 1b2-keys branch April 16, 2019 23:27
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.

None yet

2 participants