Well from what I can see this looks to cover all the bases, but wow just changing one field type has a huge impact on the component. Hope we do not break something, let me test it little more to make sure.
Well from what I can see this looks to cover all the bases, but wow just changing one field type has a huge impact on the component. Hope we do not break something, let me test it little more to make sure.
Yea 👍 I was relieved... I do not want to change more field for now... it just to big a risk. So I did these and lets see if there is any unforeseen results. So we can keep track of the all round reality of changing from a repeatable field to a subform field type. It really effects everything in relation to automation.
Yea :+1: I was relieved... I do not want to change more field for now... it just to big a risk. So I did these and lets see if there is any unforeseen results. So we can keep track of the all round reality of changing from a repeatable field to a subform field type. It really effects everything in relation to automation.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Now that was way to easy!
Well from what I can see this looks to cover all the bases, but wow just changing one field type has a huge impact on the component. Hope we do not break something, let me test it little more to make sure.
Yea 👍 I was relieved... I do not want to change more field for now... it just to big a risk. So I did these and lets see if there is any unforeseen results. So we can keep track of the all round reality of changing from a repeatable field to a subform field type. It really effects everything in relation to automation.
Thank you!