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
This means that we have to deal with two code paths, which is confusing. It would be simpler if attributes never used signature. Because there are only two legacy versions impacted, the best fix is probably to change the HTML itself rather than having code to handle this. We want our code to be as simple as possible.
The text was updated successfully, but these errors were encountered:
This PR removes the signature prop from the Attribute component and
instead, sets `attributeTypeHint` and `attributeValue`. This change
simplifies the script that was using different props for attributes
embedded in the class page and the rest.
As a side effect, this PR also fixes an issue with some default values
not showing correctly. These values were treated as signatures and
wrongly converted into HTML by a unified plugin.
Closes#1217#1252
This PR removes the signature prop from the Attribute component and
instead, sets `attributeTypeHint` and `attributeValue`. This change
simplifies the script that was using different props for attributes
embedded in the class page and the rest.
As a side effect, this PR also fixes an issue with some default values
not showing correctly. These values were treated as signatures and
wrongly converted into HTML by a unified plugin.
ClosesQiskit#1217Qiskit#1252
For attributes, we usually set
attributeTypeHint
andattributeDefaultValue
. But in Qiskit 0.19 and Provider 0.7, we instead setsignature
:This means that we have to deal with two code paths, which is confusing. It would be simpler if attributes never used
signature
. Because there are only two legacy versions impacted, the best fix is probably to change the HTML itself rather than having code to handle this. We want our code to be as simple as possible.The text was updated successfully, but these errors were encountered: