Performance implications of OPENJSON in view

Earlier today, I needed to put some small data quickly in a SQL Server database: CREATE VIEW MyView AS SELECT * FROM OPENJSON('[ ... ]') WITH ( colA int, etc. ); intending to go back and replace this with a real CREATE TABLE, INSERT INTO, etc. at some point. SQL Server isn't doing anything smart to cache or store this data, is it? It is parsing the JSON every time the view is queried, right? Just wanted to make sure before I replace it.